fix(mobile): Reconnect and Retry now on a switched-off environment switch it back on - #28628

After the tap, Android:

	main d86ee1e	branch 339d070
Android, pill	Android, main d86ee1e: pill stays	Android, branch 339d070: thread loaded
Android, terminal	Android, main d86ee1e: still disconnected	Android, branch 339d070: terminal loaded
Android, review	Android, main d86ee1e: still disconnected	Android, branch 339d070: diff loaded
Android, file preview	Android, main d86ee1e: still disconnected	Android, branch 339d070: image loaded

The branch merges main d86ee1e. The one hand-resolved part is the import block of ReviewSheet.tsx, where #34207 (Android sheets scroll without per-feature platform checks) added SheetPane and dropped cn; the merge keeps #34207's import and its restyled sheet, and drops environmentCatalog, which this branch no longer uses there. Against the live head nothing this PR does changes. On the Android emulator the Review changes screen scrolls the same on main and on the branch: one swipe up on a 124-line diff brings Note line 077 near the top on both (recording on main, recording on the branch). Both show the same development error toast on that screen ("Maximum update depth exceeded", raised from main's ReviewSheet.tsx line 585), so it does not come from this change.

Android, Review changes	top	after one swipe up
main d86ee1e	Android, main d86ee1e: Review at the top	Android, main d86ee1e: Review after one swipe, Note line 077 near the top
branch 339d070	Android, branch 339d070: Review at the top	Android, branch 339d070: Review after one swipe, Note line 077 near the top

Problem and change in full.

On mobile, an environment switched off in Settings › Environments keeps its screens open with a way to reconnect: the floating "<name> is not connected" pill on a thread, and the Retry now button on the terminal, review and file preview connection notices. Both call retryNow, which does nothing while the environment is switched off, because the supervisor ignores retries until the environment is wanted again. The pill and the notice stay, and the only way out is the switch in Settings.

#24691 fixed the same dead button on web and left the mobile notices for later.

A new useRetryEnvironment hook in features/connection reads the environment's catalog entry. If the environment is switched off (enabled === false), it switches it back on with setEnabled. Otherwise it calls retryNow as before. Every mobile reconnect control now goes through it:

• useRemoteConnections().onReconnectEnvironment, the shared handler behind the thread pill, the new-task Reconnect, Settings › Environments and Connections.
• The terminal, review sheet and file preview, in place of their direct retryNow command. The file preview still reloads after the tap, as before.

useConnectionController.retryEnvironment had no other caller and is removed, so the app has one path to retryNow from a user action. An environment that can't be switched on (unsupported, with no saved route) fails at once with the existing "environment toggle" error, the same as the Settings switch.

Method. Taps went through the T3 Device panel; the Android pill has no accessibility label, so it was tapped at its position. On main and the branch, the app was relaunched before the review step, so no diff was cached.

Both revisions ran the dev client built for main's native fingerprint, which the merge shares, with JavaScript served by Metro from each revision's own checkout, against one test server from the main checkout (the branch changes only the mobile app). The server held a sample project (one uncommitted edit, one image) and finished Replay (dev) threads.

For the file preview, the image is opened once while connected, then the environment is switched off and the preview opened again: on today's main a file screen opened with no session shows "Files unavailable" before it reaches the preview. The switch state after each tap was read in Settings › Environments (off on main, on with the merge, every control, both platforms).

Before the tap on the branch (on main the screens look the same before and after):

	iOS	Android
pill	iOS, branch 339d070: pill before the tap	Android, branch 339d070: pill before the tap
terminal	iOS, branch 339d070: notice before Retry now	Android, branch 339d070: notice before Retry now
review	iOS, branch 339d070: notice before Retry now	Android, branch 339d070: notice before Retry now
file preview	iOS, branch 339d070: notice before Retry now	Android, branch 339d070: notice before Retry now

The hook test on main d86ee1e with only the missing hook added as a stub that calls retryNow, as main's controls do:

 FAIL  |react| src/features/connection/useRetryEnvironment.test.tsx > useRetryEnvironment > Retry now with the environment enabled: false
AssertionError: expected { enabled: false, retries: 1 } to deeply equal { enabled: true, retries: +0 }
      Tests  1 failed | 1 passed (2)

On this branch (339d070):

 ✓ |react| src/features/connection/useRetryEnvironment.test.tsx > useRetryEnvironment > Retry now with the environment enabled: false
 ✓ |react| src/features/connection/useRetryEnvironment.test.tsx > useRetryEnvironment > Retry now with the environment enabled: true

Earlier runs on main 7462f23 (head 0e8284b, merge 3e094786db; iPhone 17 Pro simulator, iOS 26.5, and an Android 15 emulator, Pixel 7 profile, arm64, SwiftShader software rendering) and on main f419698 (merge ca212c1) showed the same. main has since changed ReviewSheet.tsx (#34207), so those captures are not reused.